BlueCielo Meridian Project Portal 2012 Configuration Guide | BlueCielo ECM Solutions

You are here: Exporting and importing data > Importing only documents and files > Understanding KRONOCSV files

Understanding KRONOCSV files

A KRONOCSV file is a comma-separated values (CSV) file for importing documents and their file attachments into Project Portal. The CSV file format is supported by most of the desktop applications (for example, Microsoft Office) or you can create a file using any plain text editor.

A KRONOCSV file always starts with a header. The header begins with the word KRONOCSV followed by field labels that correspond to the Project Portal properties of the documents to be imported. The remaining lines in the file contain the document property values in the order specified by the labels.

The valid field labels are described in following table.

Valid field labels
Field Label Description

KRONOCSV

Identifies the file as a Project Portal document import file. Required.

DOCID

Project Portal document identifier. If the same value appears multiple times in the KRONOCSV file, the files specified by the FILE field in those lines will be attached to the same document. If a DOCID value is omitted, the file specified by the FILE field will be attached to a unique document.

FILE

File name in the archive file to attach to the document specified by DOCID.

Document-name

Name property value.

Document-code

Code property value. Ignored if a number generator is in use in the workspace.

Authors

Author property value. If this value is omitted, the value of Creator is used.

Author-email

Author email property value. If this value is omitted, the value of Creator email is used.

Comment

Description property value.

Doctype

Code or Name of a valid document type in the workspace. Required.

Relevance

Code or Name of a valid Relevance in the workspace. Required.

Lifecycle

Code or Name of a valid document life cycle in the workspace. Required.

Status

Code or Name of a document status in the life cycle specified by the Lifecycle field. If this value is omitted, the first status in the life cycle is used.

<PropertySet>|<PropertyName>

Value of the corresponding custom property with name <PropertyName> in property set with name <PropertySet>.

Note    If the custom property is of the type Select list, specify multiple values by enclosing them in quotation marks, for example, "value1,value2,value3".

The following example shows a simple KRONOCSV file in CSV format, ready to import into a Meridian Project Portal workspace. Notice that two files will be attached to the document with the DOCID value 2. Therefore, importing this file, which specifies five files, would create a total of four documents.

KRONOCSV,DOCID,FILE,Document-name,Authors,Author-email,Doctype,Lifecycle,Relevance,Comment
,1,Transmittal Sheet .pdf,Transmittal 01234,Ernie Engineer,ernie@eleceng.com,Transmittal,,Public,
,2,First floor plan-elec.dwg,First Floor Plan - Electrical,Ernie Engineer,ernie@eleceng.com,Drawing,Approval,Public,
,2,First floor plan-arch.dwg,First Floor Plan - Architectural,Arthur Architect,art@arch.com,Drawing,,Public,Xref
,3,Second floor plan.dwg,Second Floor Plan - Architectural,Arthur Architect,art@arch.com,Drawing,,Public,Xref
,4,Elec details.dwg,Electrical Details,Ernie Engineer,ernie@eleceng.com,Drawing,Approval,Public,

Related concepts

Exporting and importing data

Related tasks

Exporting and importing complete workspaces

Exporting and importing parts of workspaces

Exporting and importing subfolders

Importing only documents and files

Importing only files

Related information

Understanding PBS files


Copyright © 2000-2013 BlueCielo ECM Solutions

www.bluecieloecm.com